Lean on hatch-vcs for managing the package version#28
Merged
Conversation
Owner
|
Thanks for the PR! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Not sure how interested you are in this, but I figure I'd might as well check.
This simplifies the mechanics of the release build a tad and means
pyproject.tomldoesn't need to be updated. It also means that__version__is now a lot cheaper to determine as_version.pywill be automatically generated with the correct information at build time.Here's an example of triggering the build with
uv buildafter creating the tagv1.2.0:And the same with
build:There should be no behavioural changes from how things currently work.